PowerShell Gallery publishing and GitHub Release creation now run as independent publish-pipeline responsibilities, so each operation reports its own outcome and a partial release can be safely retried.

Changed: Publishing and release operations are separate

Publish-PSModule now publishes the tested module artifact to PowerShell Gallery only. GitHub release creation, release notes, and release-asset upload run through the dedicated Release-PSModule action.

Technical Details

• The Plan job remains the single version authority: Publish.Module.Resolution.FullVersion is passed directly to Release-PSModule as the GitHub release tag.
• Release-PSModule detects an existing tag, resumes the module ZIP upload, and exports the final tag and release URL as action outputs.
• Gallery and release steps have independent failure behavior; cleanup only runs after a successful stable release, while abandoned-PR cleanup remains supported.
• Cleanup receives the release tag through the release action's declared output rather than shared environment state.
• The reusable workflow now uses job-scoped write permissions and a pinned Ubuntu runner; both publishing actions have action-local READMEs.
• Pester covers prefixed prerelease WhatIf behavior and resuming an existing release without recreating it. Full live publishing remains intentionally out of scope.